Labels:text | screenshot | font | black and white OCR: lelp File ftp <hostid> Open an FTP control channel to the specified remote host and enter converse mode on the new session. remote server are displayed directly on the screen. Responses from the FTP Subcommands During converse mode with an FTP server, everything typed on the console is first examined to see if it is a locally-known com- mand. If not, the line is passed intact to the remote server on the control channel. If it is one of the following commands, how- ever, it is executed locally. (Note that this generally involves other commands being sent to the remote server on the control channel . ) dir [<file>K<directory> [<local file>]] Without arguments, dir requests that a full directory listing of server's current directory be sent to the terminal. If one argument is given, this is passed along in the LIST com- the remote mand; this can be a specific file or subdirectory that is mean- ingful to the remote file system. If two arguments are given, the second is taken as the local file into which the directory list- ing should be put (instead of being sent to the console). PORT command is used before the LIST command is sent. The get <remote file> [<local file>] asks the remote server to send the file specified in the first argument. The second argument, if given, will be the name of the file on the local machine; otherwise it will have the same is on the remote machine. The PORT and RETR commands are sent on name the control channel. hash A synonym for the verbose 3 command. Is [<file> [<directory> [<local file>]] Is is identical to the dir command except that the "NLST" command is sent to the server instead of the "LIST" command. This results in an abbreviated directory listing, i.e ., one showing only file names themselves without any other information. the mget <file> [<file> .. ] Fetch a collection of files from the server. File names may include wild card characters; they will be interpreted and expanded into a list of files by the remote system using the NLST command. The files will have the same name on the local system that they had on the server . mkdir <remote directory> Creates a directory on the remote machine. put <local file> [<remote file>] Asks the remote server to accept data, creating the file named in the first argument. The second argument, if given, will be the name of the file on the remote machine; otherwise it will have the same name as on the local machine. mands are sent on the control channel. The PORT and STOR com- rmdir <remote directory> Deletes a directory on the remote machine. type [alill <bytesize>] Tells both the local client and remote server the type of file that is to be transferred. The default is 'a', which means ASCII (i.e ., a text file). Type 'i' means image, i.e ., binary. In ASCII mode, files are sent as varying length lines of text in ASCII separated by cr/lf sequences; in IMAGE mode, files are sent exactly as they appear in the file system. ASCII mode should be used whenever transferring text between dissimilar systems UNIX and MS-DOS) because of their different end-of-line and/or Ceg . end-of-file conventions. When exchanging text files between machines of the same type, either mode will work but IMAGE mode is usually faster. Naturally, when exchanging raw binary files (executables, compressed archives, etc) IMAGE mode must be used. Type 'l' (logical byte size) is used when exchanging binary files with remote servers having oddball word sizes (eg. DECSYSTEM-10s and 20s). Locally it works exactly like IMAGE, except that it notifies the remote system how large the byte size is. bytesize is typically 8. The type command sets the local transfer mode and generates the TYPE command on the control channel. verbose [011121314] Set or display the level of message output in file transfers. Verbose 0 gives the least output, and verbose 3 the most, as fol- lows : 0 - Display error messages only. 1 Display error messages plus a one-line summary after each transfer giving the name of the file, its size, and the transfer time and rate. 2 Display error and summary messages plus the progress messages generated by the remote FTP - Display all messages. In addition, a "hash mark" server . 3 (#) is displayed for every 1,000 bytes sent or received. 4 Display all messages. In addition the number of bytes sent/received are displayed after each acknowledged packet. If a command is sent to the remote server because it is not recognized locally, the response is always displayed, regardless of the setting of verbose. This is necessary for commands like pwd (display working directory), which would otherwise produce no message at all if verbose were set to 0 or
(.png)
